CICA 1995 September (Japanese)/CICA Shareware for Windows CD-ROM (Walnut Creek) (September 1995) (Japanese) (Disc 1).iso/disc1/misc/ndw.faq

Text File | 1995-09-05 | 41.0 KB | 884 lines

Frequently Asked Questions for NDW

Section 1 - Install

1.1 - Sharing Violation while copying last disk or while Creating Groups.
1.2 - Error expanding WIN.INI or SYSTEM.INI
1.3 - Install fails when trying to restart Windows
1.4 - After choosing the drive to install NDW on or after installing when Windows
      is restarting, the install hangs.
1.5 - Windows indicates an error involving symunzip2.dll.
1.6 - Error when SHELL.DLL is being copied (approximately 3%).


Section 2 - Startup Errors
2.1 - Since upgrading to NDW 3, I frequently get thrown out of Windows to a
      DOS prompt or a completely black screen. Is there anything I can do
      to make NDW run on my system?
2.2 - Why do I get a Sharing Violation error message whenever I change
      video modes and then restart Windows?
2.3 - Why can't NDW find its files? It reports about 7 missing ones
      including NDWCFG.DLL, TREASURE.DLL, and NWIN2.DLL, ETC.
2.4 - Why does NDW say, "Can not start NDW as the Shell"?
2.5 - WHy does NDW say, "Error Loading PROGMAN.EXE"?
2.6 - Why do all the items in a group other than my StartUp group run when
      I load NDW?
2.7 - Why does NDW say, "Unable to verify product registration" when I try
      to run it?
2.8 - Why does NDW report a General Protection Fault at 0004:03FC? I'm
      using NDW 2.0.
2.9 - Why does Windows say "VNDWD.386 not installed...."?


Section 3 - General GPFs
3.1 - Why does NDW produce a General Protection Fault error when I try to
      change the associations by choosing Associate in NDW?
3.2 - Why can't I use WIndows communications programs to transfer files
      since installing NDW 3?


Section 4 - Layout and Tools
4.1 - How do I get rid of items added to the main menu and the drive window
      menu's?
4.2 - Why does NDW show all of my icons as black and white blobs after I
      have changed video drivers?
4.3 - I've reset my icons and many of them have switched to the generic one
      How do I get the correct icon back?
4.4 - Why does NDW change my icons when I add a new icon to a Norton Icon
      Library?
4.5 - Why doesn't NDW keep the custom icon for DOS applications in the
      Startup group?
4.6 - Why doesn't double-clicking the right mouse button on the desktop
      bring up Quick Access? And why aren't the Quick Access groups listed
      on the Window Window menu?
4.7 - How can I prevent NDW from realigning my drive icons whenever I
      refresh a drive window?
4.8 - Why doesn't NDW align desktop buttons correctly? Particularly, I
      can't put anything in the top-right corner.
4.9 - Why doesn't NDW save my configuration even though the check-box to
      save on exit is on and I've tried saving manually?
4.10 - Why can't I get NDW to display my printer icon?
4.11 - Why can't I use all of the commands I've added to the Launch List?
4.12 - How can I reduce the size of buttons on the NDW toolbar?
4.13 - I tried to use SuperFind to find some files but it reported no such
       files existed. I was certain I had the files so I searched with a
       drive window and after checking several directories, I finally found
       them. What's wrong with SuperFind?
4.14 - Sometimes, I will start NDW and a group that I normally don't have
       open is opened. How do I keep NDW from changing my group setup?
4.15 - Why can't I use the Compare command on Desktop Editor's File menu?
4.16 - How do I get rid of the treasure chest buttons?
4.17 - When I start Windows, I get a picture of a computer and "The Norton
       Desktop" while NDW loads. How do I stop this so I can see my
       wallpaper?
4.18 - How do I prevent Sleeper from complaining that it can't update one of
       its modules configurations?
4.19 - How do I get Sleeper to show me all of my After Dark modules?
4.20 - I like File Assist but I can't get it to appear in all of my Windows
       applications. How do I get it to appear if it doesn't appear by
       default?
4.21 - Why doesn't File Assist appear when I use Word for Windows?
4.22 - I am using File Assist in Word for Windows and when I try to save to
       an alternate format, I get the wrong file format. How do I get File
       Assist to save to the correct format?


Section 5 - Problems Launching Applications
5.1 - Why do all of my WIndows programs start minimized?
5.2 - Why has NDW suddenly started getting slower - particularly the
      groups?
5.3 - How can I get NDW to recognize environment variables in the
      Properties of an icon?
5.4 - Why can't I run any DOS applications - including Command.Com?
5.5 - Why does NetWare report that it is unable to load Unicodes? This
      works fine with Program Manager as the shell.
5.6 - Why doesn't NDW keep the icon I have set for DOS applications in the
      StartUp group?


Section 6 - Drive Windows
6.1 - Why won't the Disk Format in NDW make bootable diskettes?
6.2 - Why does opening a drive window on my Bernoulli drives cause them to
      be dismounted? They are being mounted by DoubleSpace.
6.3 - Why don't my NDW 2.0 drive windows have a scroll bar?
6.4 - Why do I get the error message, "Not enough file handles" when
      opening a drive window?
6.5 - Why don't any files appear in the drive windows? The directories show
      up but every one shows "No Files Found"
6.6 - Why won't NDW show me drive icons for A: and/or B:?
6.7 - Why won't NDW show me a drive icon for my compressed drive?
6.8 - Why won't the drive windows show anything except the last 3 digits of
      the file sizes?
6.9 - When I have two drive windows open, NDW crashes when I try to close
      the second one. Sometimes, I can't even open the first one. How do
      I get NDW to work with my drives?
6.10 - I have some File Manager extensions that appear in File Manager but
       I cannot get them to show up in NDW? Will these work in NDW?
6.11 - Why does NDW exit out to DOS if I try to open a drive window with an
       audio CD in my CDROM drive?
6.12 - How do I prevent NDW from deleting directories by accident? I've
       used the right mouse button to select files which left directories
       selected and NDW delete those too.
6.13 - How do I get the volume labels for floppy disks to appear in the
       drive window? I get the drive labels to appear in the drive windows
       for all my hard drives and network drives but not the floppy drives.
       If I go to the Label Disk item under the Disk menu in NDW, I can see
       the label.


Section 7 - System Information
7.1 - Why does System Information show a negative amount of RAM available?
7.2 - Why does System Information shows a very low benchmark when I have
      what should be a very fast system?
7.3 - Why does System Information show me the incorrect system files?




Section 1 - Install

1.1 - Sharing Violation while copying last disk or while Creating Groups.

There is a conflict between Share and SmartCan. Disable either of those TSRs,
set SHELL= to PROGMAN in SYSTEM.INI and rerun Install.

1.2 - Error expanding WIN.INI or SYSTEM.INI

Check the WIndows directory for SYSTEM.* WIN.* and NDW.*. Delete any file
with a $, ! or _ as the last Character. Example: NDW.IN$. Then Start
install again.

1.3 - Install fails when trying to restart Windows

Check the TEMP environment variable for a trailing backslash or space. You
can avoid future problems by editing AUTOEXEC.BAT and making sure the
backslash and/or space is removed from the SET TEMP line.

1.4 - After choosing the drive to install NDW on or after installing when
Windows is restarting, the install hangs.

Use the "ATTRIB -r" command to turn off the read only attribute on
autoexec.* and config.* in C:\ and system.*, win.* and ndw.* in the Windows
directory. Restart the install program.

1.5 - Windows indicates an error involving symunzip2.dll.

Copy disk 1 to a temporary subdirectory on the hard drive (but not the
directory where the TEMP environment variable is set. It may also be
necessary to use a stripped-down conffiguration by preparing a bootable
floppy with a config.sys that loads HIMEM.SYS and sets FILES=50. In
addition, the autoexec.bat for this disk should set TEMP to a directory on
an uncompressed drive(if possible) with at least 1MB free and a path to
Windows, DOS and NDW.  If there is an error coping the diskette over in
preparation for this, the disk itself is proably bad. Contact Customer
Service for a new diskette.

1.6 - Error when SHELL.DLL is being copied (approximately 3%).

Make a copy of Disk #1 to either a directory on the hard drive or to
another floppy disk. Edit INSTALL.INF on that copy and search for
SHELL.DLL. This should show a line that reads:

SHELL.DLL,     TARGET

Place a semicolon (;) at the beginning of the line and restart the
install from the copy of the first disk and use the remaining disks as
normal.

Section 2 - Startup Errors


2.1 - Since upgrading to NDW 3, I frequently get thrown out of Windows to a
DOS prompt or a completely black screen. Is there anything I can do to make
NDW run on my system?

There are several things to check here. First, if you use NAVTSR or
NAVTSRW, go into NAV in DOS and choose Options from the Tools menu. Choose
the AutoProtect category and click the Startup button. Under the group of
options labeled "Types of Memory to Use", turn off the option for "Expanded
Memory (EMS)". Click OK to get back to the main dialog and click Options
dialog and click the Advanced button. In the Check Floppies group, turn off
the checkbox for "Check Floppies For Boot Viruses Upon Access". Click OK
until you're back at the main NAV screen, exit NAV and reboot to allow
those changes to take effect.

Also, check CONFIG.SYS and make sure there is a FILES= setting and that
this is set to at least 50. Make sure there is a BUFFERS= setting and this
is usually best when set to a multiple of 8. 16 is normally sufficient but,
in some cases, 24 may be better.

More importantly, check the SHELL= setting and make sure the environment
size is set to at least 1024 and 2048 is recommended. If there is no SHELL=
setting, refer to your DOS manual on how to add this and add a setting to
specify the number of bytes reserved for environment variables.

One other thing you might want to try is adding the line
"EMMExclude=A000-FFFF" to the [386Enh] section of system.ini in the
Windows directory. This will keep Windows itself out of the upper memory
area and let the DOS memory manager control that region.

Finally, before attempting to restart Windows, go to the NDW directory and
delete ICOCACHE.DAT. It may be a simple matter of NDW trying to overwrite
this file and running into a problem with SHARE.EXE or VSHARE.386.

2.2 - Why do I get a Sharing Violation error message whenever I change
video modes and then restart Windows?

When you change video configuration, NDW will update some files when you
restart Windows and this can trigger a sharing violation. To prevent this,
delete the file ICOCACHE.DAT in the NDW directory before restarting Windows
with the new video driver. This means that you should not click the Restart
Windows button in the Windows Setup program since this will not give you
the chance to delete that file. Either use the DOS-based Setup program in
the Windows directory or exit Windows after changing video drivers, delete
the file and restart Windows.


2.3 - Why can't NDW find its files? It reports about 7 missing ones
including NDWCFG.DLL, TREASURE.DLL, and NWIN2.DLL, ETC.

Most often, this caused by NDW not being in the path. Check the
autoexec.bat for multiple path lines and make sure that all lines after the
1st PATH setting refer to "%PATH%" so they will add to the path rather than
reset it.

If the NDW directory does appear in the path then check the path at a DOS
prompt with the SET command to ensure NDW is there. If the path is very
long, NDW may not fit since DOS limits the path to 127 characters.

If the path is correct check for a WIN.BAT or a WINSTART.BAT or a network
login batch file that changes the Path. If all else fails set the path to
C:\NDW;C:\WINDOWS;C:\DOS (i.e. just set the path to the NDW, WIndows and
DOS directories) so we are certain of the path when Windows starts.

2.4 - Why does NDW say, "Can not start NDW as the Shell"?

NDW is unable to load the .DLL files it needs to run as the shell. To
correct:

    1)  Try running PROGMAN as the shell, then running NDW as an app.
        A. If this works, more than likely the path is incorrect. Check
           for a path that is more then 127 Characters. If this is the
           case, reduce the number of entries on the path.

    2) If it will not run as an app, try the following:
        A. Increase the environment space to at least 1024.

        B. Increase the file handles to at least 60(3.0 requires 50
           minimum).

        C. Be sure there is enough XMS free with the MEM command NDW 2.x
           will need 2MB while NDW 3 requires 4MB.

        D. Delete the .EXE's and .DLL's from the NDW directory and
           reinstall NDW. An individual .DLL may be damaged or missing and
           it is normally faster than easier to reinstall than try to
           determine which one(s) is(are) missing.

2.5 - WHy does NDW say, "Error Loading PROGMAN.EXE"?

This is usually caused by the Microsoft or Central Point Anti-Virus. MSAV's
default creates checksum files for all program files on disk during a scan.
If a program is updated or added after the initial scan, the checksum file
is not automatically updated.  It is then  allowed to execute, but not to
open any other files.  The result is that NDW.EXE executes as shell, can
not run NDWMAIN,  and  cannot run PROGMAN, resulting in the error.

To correct this, delete CHKLIST*.* from all directories or start MSAV,
choose Options, check Create New Checksums, and rescan each drive. Or
remove MSAV from WIN.INI and CONFIG.SYS.

Another possibility is that the shell= in the SYSTEM.INI is incorrect.
A failed install may leave the shell set to the install program or the
program name is incorrect or misspelled. Setting this to load NDW.EXE with
the full path to the NDW directory should correct this.

2.6 - Why do all the items in a group other than my StartUp group run when
I load NDW?

NDW has set the StartUp group incorrectly. To fix this, go to the Quick
Access settings in Control Center and click the AutoStart button. Make sure
the group you want selected has the checkmark next to it.

2.7 - Why does NDW say, "Unable to verify product registration" when I try
to run it?

This is most often caused by a failed install where the Windows shell is
still set to INSTALL.EXE. This occurs most often when chhosing the Reboot
option after installation and the disk cache does not have time to flush
completely. To correct this, change the shell= setting in SYSTEM.INI in the
Windows directory to NDW.EXE with the full path to the NDW directory
specified. Also, check in the [386Enh] section and verify that NDW has
added lines such as these:

device=symevnt.386
device=vfintd.386
device=vnss.386


2.8 - Why does NDW report a General Protection Fault at 0004:03FC? I'm
using NDW 2.0.

This is usually a problem in of NDW's group files and almost always in
QAMAIN.QAG. In the NDW directory, delete QAMAIN.QAG then try to start
Windows. Assuming Windows loads OK, open a drive window for the drive that
Windows is installed on and hit the Tab key to move to the file pane. Go to
the View menu, choose Filter, choose Custom and type "*.QAG". Click OK, go
to the File menu, choose Select, and choose All from the secondary menu.
All the files listed in the drive window should now be selected. Position
the drive window and the Quick Access window so that both can be seen and
then drag the files from the drive window to the Quick Access window.
Either all of them will become group icons in the Quick Access window or
you will get a GPF. If you get a GPF, reboot and restart Windows. Then open
a drive window for the Windows directory again but this time, drag the QAG
files to Quick Access one by one to determine which one causes the crash.
Once you have isolated this, you should be able to drag all of the QAGs -
except QAMAIN.QAG - in the NDW directory into Quick Access. Once you have
added all the groups back that you can, you can then save your
configuration.

If you don't get a GPF, select the NDW directory in the drive window and
drag each QAG - except QAMAIN.QAG - from the file pane to Quick Access
until you find the one that is corrupt. Again, restart Windows and continue
adding groups until you have recovered all of the groups except the
corrupted one.


2.9 - Why does Windows say "VNDWD.386 not installed...."?

Search all local hard drives for VNDWD.386 and be sure there is only one
occurrence, in the proper directory (\NDW  for 2.2, \windows\system for
previous versions).  Then check the date and be sure it is the same as the
NDW.DLLs. If it is search the entire drive for n*.DLL and be sure all
Desktop DLLs on the disk are the same date.


Section 3 - General GPFs

3.1 - Why does NDW produce a General Protection Fault error when I try to
change the associations by choosing Associate in NDW? This works fine in
File Manager and I can edit these in WIN.INI.

Edit WIN.INI and check for two possible problems. First, do a search for
the word "extensions". If you find it anywhere beside the [Extensions]
section header, misspell the word (for example, remove the 1st "e".)
Second, put the cursor on the first line within the [Extensions] section
and hit the End key. If the cursor goes past the last character in the
line, backspace to remove any trailing spaces. hit the down arrow and the
End key to do the next line. Repeat this for each line in the [Extensions]
section. Also, check for invalid entries in the [Extensions] section of the
Win.ini - such as an entry that doesn't have an extension associated to it.
Once this is done, restart Windows and the Associate command should work
properly.


3.2 - Why can't I use WIndows communications programs to transfer files
since installing NDW 3? The transfer begins but then Windows crashes.

This is caused by a conflict between File Assist and the way some
communications programs open a file that is being received. Run your
telecommunications program and bring up the File Save As or File Open
dialog box (how to do this will depend on the application in question) and
click the "Config" button listed along the bottom of the dialog with the
File Assist extensions. Turn off the checkbox labeled "File Assist Enabled
For:" and File Assist will ignore that one application. If you use more
than one Windows communications program, you will need to do this for each
one individually.


Section 4 - Layout and Tools


4.1 - How do I get rid of items added to the main menu and the drive window
menu's?

Edit WINFILE.INI in the Windows directory and delete or comment out the line
for this File Manager add on from the [AddOns] section.

4.2 - Why does NDW show all of my icons as black and white blobs after I
have changed video drivers?

The icons are cached in a separate file so that NDW doesn't have to reread
these every time a group is opened. To rebuild this file with the new
settings, choose Customize from the Options menu, click Quick Access, click
Adavanced and click Reset Icons. Alternatively, go to the NDW directory
before starting Windows and  delete ICOCACHE.DAT.

4.3 - I've reset my icons and many of them have switched to the generic one
How do I get the correct icon back?

Try Reset Icons as described in 4.2 but first verify that the FILES=
setting in CONFIG.SYS is at least 50. Also, make sure that the file that
the icon is supposed to come from still exists. If that file has been moved
or renamed, NDW will just use the generic icon rather than issue a warning
message.

4.4 - Why does NDW change my icons when I add a new icon to a Norton Icon
Library?

When adding new icons to a library, it is necessaery to append the new icon
to the end of library. NDW and Program Manager will keep a pointer to
indicate which icon to use when specifying a file with multiple icons and
inserting icons will throw the pointers off.

4.5 - Why doesn't NDW keep the custom icon for DOS applications in the
Startup group?

The ability to set an icon for a DOS application requires carrying on a DDE
conversation with the module in WIndows that actually handles the DOS
application. The code to handle this is not loaded until after the
processing of the StartUp group and so NDW does not respond when WINOLDAP
asks for this information. This yields a decrease in the time needed to
load Windows and NDW.

4.6 - Why doesn't double-clicking the right mouse button on the desktop
bring up Quick Access? And why aren't the Quick Access groups listed on the
Window Window menu?

Quick Access is not currently loaded. In NDW 2.x, go to Configure,
Preferences, Advanced and turn on Load Quick Access. In NDW 3, go to
Options, Defaults, Advanced and select Load Quick Access.

4.7 - How can I prevent NDW from realigning my drive icons whenever I
refresh a drive window?

Set AlignDrives=0 in [Defaults] section of NDW.INI.

4.8 - Why doesn't NDW align desktop buttons correctly? Particularly, I
can't put anything in the top-right corner.

To change how buttons realign, adjust SnapFactorX and SnapFactorY in
[Defaults] section of NDW.INI. In NDW 3, this can be modified in the
Desktop Layout section of Control Center. Making these values smaller
should help improve the ability to fine tune where buttons are placed.

4.9 - Why doesn't NDW save my configuration even though the check-box to
save on exit is on and I've tried saving manually?

This almost always indicates a problem updating NDW.BIN. Before starting
WIndows, go to the NDW directory and rename this file to something else
such as NDW.NIB. Start Windows, make some configuration changes, save the
configuration, exit and restart Windows. All the changes should still be
there. Unfortunately, most of the customization you have made previoulsy
will be lost in this process since NDW.BIN holds the bulk of the NDW
configuration but that should correct the problem you're seeing. After
verifying this has corrected the problem, delete the renamed NDW.BIN.

4.10 - Why can't I get NDW to display my printer icon?

If you have recently changed printers in Control Panel, reselect the
printer button in the Tool Icons section of Control Center. In NDW 2.2 and
earlier, this is in the Preferences - Printers dialog.

If the printer is selected properly, this may indicate a problem in
updating NDW.BIN. Follow the steps outlined in 4.9 above and that should
correct this.

4.11 - Why can't I use all of the commands I've added to the Launch List?

This menu is limited to 29 items - additional items are displayed, but do
not function.

4.12 - I am running my VGA in 1024x768 mode.  When I installed NDW 3.0, the
icons on the toolbar were small and I assumed I could add a lot more. When I
changed the toolbar, the icons got bigger. How can I get them small
again?

The icons are all sized evenly and the size will be set so that the longest
label will fit. In the toolbar editing screen, look for the button with the
longest label, modify it and give it a shorter label. The icons will then be
resized to conform to whatever is the longest label at that point. To get
the absolute maximum number of buttons, turn off the text altogether.

4.13 - I tried to use SuperFind to find some files but it reported no such
files existed. I was certain I had the files so I searched with a drive
window and after checking several directories, I finally found them. What's
wrong with SuperFind?

Open Superfind and press Alt-X to move to the With Text field. Hit Delete
to make sure there is nothing in that field. There may be either one or
more spaces there or some characters that don't display normally and so the
box appears empty. If SuperFind still won't find the required files, check
the Attributes settings and make sure the boxes for Read-Only, Archive,
System and Hidden are all greyed and the one for Directory is clear.

4.14 - Sometimes, I will start NDW and a group that I normally don't have
open is opened. It seems to think that Save Configuration on exit is
turned on even though I have turned it off and saved the configuration.
How do I keep NDW from changing my group setup?

The original design in NDW 1 was that NDW would not save anything about the
configuration if you turned Save Configuration on Exit off. However, we
received numerous complaints from people who had this option turned off,
installed a new application that then required them to restart Windows or
at least exit to DOS and they would loose the group that had just been
created. This could also happen if they had been customizing the groups and
forgot to save before exiting. In NDW 2, we added a flag so NDW will know
if you do anything to your groups like adding or deleting an item and the
exit code checks that flag. If it is set, NDW saves the group configuration
so those group changes won't get lost. However, it seems like NDW gets
confused on just what exactly constitutes a group change and may be setting
this flag when you merely open a group that is normally closed or move the
group to a different position. With NDW 3, you can add the line Autoclave=0
to the [Quick Access] section of NDW.INI in the Windows directory. This
will still keep the safety feature in place (there is no way to completely
disable it) but it should eliminate most of the unwanted group
configuration saves.

4.15 - Why can't I use the Compare command on Desktop Editor's File menu? I
click it but nothing happens even though it is enabled.

This will happen if NDW is not the shell and is not running. NDW must be
running for Compare to work.

4.16 - Now that I've installed NDW 3, I have little pictures of treasure
chests on the title bars of all my NDW windows. How do I get rid of them?

Run Desktop Editor or Notepad and open SYMCFG.INI in the Windows directory.
If this file does not exist, just use the editor to create a new file. Add
the following lines:

[Treasure]
Buried=1

and save it to your Windows directory as SYMCFG.INI. Exit and restart
Windows. The treasure chests will be gone from the title bars but
they'll remain in the dialog boxes.

4.17 - When I start Windows, I get a picture of a computer and "The Norton
Desktop" while NDW loads. How do I stop this so I can see my wallpaper?

First, edit NDW.INI in the Windows directory and add the line
NDWSplashScreen=0 to the [Defaults] section. Also, go to the NDW directory
and delete the file NDWSPLSH.BMP.


4.18 - When I start Windows, everything comes up fine except Sleeper which
tells me it is unable to update one of its modules configurations.

This happens when there is a problem updating NDW.BIN. See the answer to
4.9 above.

4.19 - Sleeper does not show me all of my After Dark modules even though I
have installed After Dark and I can see the modules in After Dark. How do I
get Sleeper to find these modules?

If you have After Dark 1.0, make sure you have an AD_PREFS.INI in the
Windows directory and that that file has an [After Dark] section and that
section has a Path= setting which points to the correct drive and directory
for After Dark.

If you have After Dark 2.0 or later, you'll also need to make sure you have
the ADRUNNER.NSS or AFTERDRK.NSS (there are two possible versions) in the
AD directory. If it still doesn't work, copy that module to the NDW
directory and rename it to anything that does NOT start with an "a" - for
example, B4DARK.NSS. Then start Sleeper and it should list the module
"After Dark Runner". Be sure not to select the module listed as "(MS) After
Dark Runner". This module is designed to be run from Windows itself through
Control Panel and having Sleeper use it to start After Dark can cause
Windows to hang.

4.20 - I like File Assist but I can't get it to appear in all of my Windows
applications. How do I get it to appear if it doesn't appear by default?

File Assist can only link itself to applications that use the common
Windows 3.1 dialog boxes for File Open and File Save As. Unless an
applications uses those dialogs, it can not use File Assist.


4.21 - Why doesn't File Assist appear when I use Word for Windows?

The macros probably are not loaded. If you have installed the update for
NDW 3, run Word for Windows and open FASSIST.DOC from the NDW directory.
Double click the line of text in italics that reads:

       -->Install FileAssist Macros<--

After that, File Assist should attach itself to the File Save As and File
Open dialogs in Word.

If you have not installed the NDW 3 update, do not install the File Assist
macros for Word until you have done so. The originaly macros will cause
some problems with the Word dialogs and should not be used.


4.22 - I am using File Assist in Word for Windows and when I try to save to
an alternate format, I get the wrong file format. How do I get File Assist
to save to the correct format?

Download NDW3UP.EXE from library 3 of the SYMUTIL forum or from the
Symantec BBS and use it to update the macros. This should correct the
problem. If it still fails, check WINWORD6.INI in the WINWORD directory and
make sure the following lines appear:

[MSWord Text Converters]
MS-DOS Text with Layout=MS-DOS Text with Layout,C:\WINWORD\TXTWLYT.CNV, asc
Text with Layout=Text with Layout, C:\WINWORD\TXTWLYT.CNV, ans

Make sure "C:\WINWORD" actually specifies the correct path to Word for
Windows. If there are any other lines in that section, delete them or
comment them out by placing a ";" at the very beginning of the extra lines.


Section 5 - Problems Launching Applications

5.1 - Why do all of my WIndows programs start minimized?

Use SuperFind (or any such tool) to search for SHELL.DLL and delete any
copies not in the \windows\system directory dated 3-10-92 (if you are using
(WORKGROUPS 3.11 the date will be 11-1-93). If there is one in there with a
different date, reload the one from the Windows disks there. To decompress
this, copy the file SHELL.DL_ to the \windows\system directory and enter:

expand shell.dl_ shell.dll

Then delete *.dl_. Start Windows and programs should run normally.

5.2 -  Why has NDW suddenly started getting slower - particularly the
groups?

NDW keeps the icons for the group items in a cache file which normally
allow it to work much more quickly but as time goes by, this cache file
which become filled with obsolete information. Before starting Windows, go
to the NDW directory and delete ICOCACHE.DAT. NDW will rebuild the cache.
Note that it will be necessary for it to reread all of the icon files at
that time so if these files have been moved or deleted, the items they were
used for will resort to the generic icon.

5.3 - How can I get NDW to recognize environment variables in the
Properties of an icon?

   A.  For DOS apps, you can use a .PIF and specify the values there.

   B.  For Windows apps, create a script such as:
       sub main
           ChDrive Environ$("TEMP")
           ChDir Environ$("TEMP")
           tid = Shell("myapp")
       end sub

5.4 - Why can't I run any DOS applications - including Command.Com?

There are several possible causes. First, check in CONFIG.SYS for two
things - make sure that the environment space is set to at least 1024 bytes
and 2KB is even better and make sure that the FILES= statement is set to at
least 50. If they aren't change those settings and reboot and see if that
helps.

If those were OK or if changing them doesn't help, start Windows in
enhanced mode and run SysInfo. Click the 2nd button and look at how much
free disk space is available on the drive where your TEMP environment
variable is set. If this is less than 2MB, try freeing up some space on
that drive or set TEMP to a drive that does have 2MB or more available.
When checking TEMP, you might also want to determine what COMSPEC is set to
and make sure this is correct; NDW and/or Windows may be failing to load
the command processor if this is not set correctly.

In addition, you might want to check the Virtual Memory settings in Control
Panel in the 386 Enhanced section and make sure the swapfile is not being
created on a compressed drive.

Also, in the windows\system directory, use expand on commdlg.dll,
shell.dll, ver.dll, and toolhelp.dll. Then do a superfind on these files
and remove them from any other directory you find them in.

Finally, there's a couple of odd remedies that may or may not apply. First,
check if there is a MAXBPs= setting in the [386Enh] section of SYSTEM.INI.
If not, try adding:

MaxBPs=768

to that section and see if that helps.

The other one is to see if there is a TimerCriticalSection= setting in
SYSTEM.INI and, if there is, try commenting it out. Let me know how it
goes.

One last thing to check is a problem with the 386GRABBER. If you use the
WIndows Setup program to switch the video driver to any other driver and
then switch it back, this should update the driver. When switching away,
it doesn't matter if the other driver is already on the hard drive and will
actually make this process faster if it is. What is critical is that when
you reinstall the video driver and it reports there is currently a copy of
that on the hard drive, tell it to overwrite that driver so that WIndows
will reload this from the floppies and overwrite the driver files.

5.5 - Why does NetWare report that it is unable to load Unicodes? This
works fine with Program Manager as the shell.

When NDW is the Windows shell and you are connected to NetWare 4.0x, you
must make sure that the directory that contains the Unicodes is in the
DOS PATH. Add this directory to the PATH and Windows and NDW will load
properly.

5.6 - Why doesn't NDW keep the icon I have set for DOS applications in the
StartUp group?

NDW does not maintain the custom icons of DOS applications in the StartUp
group and will sometimes not use custom icons for DOS applications that are
run normally. The 1st is a design decision; communicating that information
adds some overhead to NDW's load time and we try to minimize that as much
as possible. The failure to retain those icons at other times is being
looked into by the NDW development team.



Section 6 - Drive Windows

6.1 - Why won't the Disk Format in NDW make bootable diskettes?

This usually occurs when the boot drive has been swapped via Stacker,
DoubleSpace, or some othe disk compression program. The boot record from
the swapped drive is copied to the floppy, making it unbootable. You can
make the disk bootable later with the SYS command in DOS.

6.2 - Why does opening a drive window on my Bernoulli drives cause them to
be dismounted? They are being mounted by DoubleSpace.

This is a problem with the Bernoulli drives and DoubleSpace - Iomega is
working on a fix.

6.3 - Why don't my NDW 2.0 drive windows have a scroll bar?

That version of NDW would have this problem with custom drive windows. You
can use that version and avoid this problem if you use the Norton Desktop
Defualt setting for the drive windows.

6.4 - Why do I get the error message, "Not enough file handles" when
opening a drive window?

The files NDW uses to record the directory tree structure are damaged. Go
to the root directory of that drive and delete the TREEINFO.* files. Open a
drive window for the drive and rescan the drive.

6.5 - Why don't any files appear in the drive windows? The directories show
up but every one shows "No Files Found"

Under the View menu, choose Filter and verify that the check boxes for the
Archive and ReadOnly attributes are set to grey (the 3rd state in these 3
state checkboxes) and clear the boxes for Hidden and System. Then click the
Set Defaults button and the OK button.

6.6 - Why won't NDW show me drive icons for A: and/or B:?

There are two common causes for this - either DRIVER.SYS is being loaded in
CONFIG.SYS or there is disk compression software active and it is
AutoMounting compressed floppies. Remove DRIVER.SYS and/or disable
AutoMounting and the drives will be able to be displayed.

6.7 - Why won't NDW show me a drive icon for my compressed drive?

Make sure the drive is selected under Options/Configure/Drive Icons. If it
is selected and is not showing Click Refresh. Quit Windows and restart. If
the drive is gone again then there is a problem updating NDW's
configuration file. Open a drive window for the NDW directory and delete
NDW.BIN. Save the configuration to rewrite this file with the current
settings and then try configuring the drive icons again.

6.8 - Why won't the drive windows show anything except the last 3 digits of
the file sizes?

Go to Control Panel, International, and enter a Thousands Separator. If
this is set to nothing, this will occur; setting it to anything - even a
space - will avoid this.

6.9 - When I have two drive windows open, NDW crashes when I try to close
the second one. Sometimes, I can't even open the first one. How do I get
NDW to work with my drives?

NDW will load the File Manager add-ins that are listed in WINFILE.INI in
the Windows directory and some of these add-ins are not designed to have
more than one copy of themselves loaded. When the 2nd copy is unloaded,
this causes the system to crash. To correct this, exit Windows, go to the
Windows directory and edit NDW.INI. Go to the [Defaults] section and change
the MaxWinFileExtensions to 0. NDW will no longer try to load the add-ins
and won't run into problems with add-ins that don't want more than one
instance loaded.


6.10 - I have some File Manager extensions that appear in File Manager but
I cannot get them to show up in NDW? Will these work in NDW?

Before starting Windows, go to the Windows directory and edit NDW.INI. Go
to the [Defaults] section and change MaxWinFileExtensions=10 (or 0) to
MaxWinFileExtensions=100. Save that and start Windows and the add-ins
should come up fine. If they still don't appear, run NDW's Control Center,
choose the Defaults category and click the Advanced button. Turn on the
option for "File Manager Extensions on Main Desktop Menu" and they should
then appear on NDW's main menu.


6.11 - Why does NDW exit out to DOS if I try to open a drive window with an
audio CD in my CDROM drive?

The problem arises because the CDROM drivers do not provide a way to ask
about the status of the drive(s) it controls without it having to read data
from a disk. NDW polls all the installed devices whenever it needs to know
about the drives (mainly, to see if they're still active) and so it gets
the system error reading the CDROM. You might check to make sure you have
the latest versions of MSCDEX and whatever custom driver your CDROM drive
requires since newer drivers often do add this capability and can prevent
the error. If you do have the latest version of these drivers and if you
have SmartCan loaded, try disabling SmartCan in autoexec.bat as SmartCan
can sometimes cause this to happen also. Otherwise, the only workaround is
to keep a data CD in the drive.

6.12 - How do I prevent NDW from deleting directories by accident? I've
used the right mouse button to select files which left directories selected
and NDW delete those too.

The ability to extend file and directory selection with the right mouse
button without having to use ctrl and/or shift-click combinations is one of
the most powerful and most deadly of the NDW extensions.

There's two way to deal with this: (A) never forget to left click on the
first directory or file when making a selection and then use the right
mouse button to add files or, (B) go into NDW's Control Center and go to
the Drive Windows category. Click the Advanced button in set the options
for Right Mouse Button to Pop-up Menu. OK your way back out and then try a
right click on a file or directory. Instead of extending the selection,
you'll get a menu of commands from the File menu to act on the selected
items. This means you'll have to use Shift click to extend multiple files
in the selection and Ctrl-click to add entires one by one but it is much
safer.

6.13 - How do I get the volume labels for floppy disks to appear in the
drive window? I get the drive labels to appear in the drive windows for all
my hard drives and network drives but not the floppy drives. If I go to the
Label Disk item under the Disk menu in NDW, I can see the label.

The problem is that the entries in the drive list are updated every time
there is drive access. If we include the labels for floppies, this would
cause two problems: A) if there wasn't a disk in the drive, NDW would wait
for the timeout on the drive and B) if there was a disk in the drive, you'd
need to wait for NDW to read this information and that takes almost as long
as the timeout. So, we removed this early on in the NDW 1 development to
speed things up with NDW's drive access. So, there is no way to determine
the label of a floppy disk in the drive window. You can see the label in
the Label Disk dialog.


Section 7 - System Information

7.1 - Why does System Information show a negative amount of RAM available?

SysInfo is limited to 32MB or RAM. With more than 32MB, SysInfo's internal
variable overflows and becomes negative.

7.2 - Why does System Information shows a very low benchmark when I have
what should be a very fast system?

This can happen with a disk cache over 1.5 MB. Check also Stealth mode
(QEMM) or other Programs that might slow the system down (screen savers,
schedulers, etc. Part of the problem is that the benchmark doesn't have
complete control of the CPU and can be interrupted during the test.

7.3 - Why does System Information show me the incorrect system files?

There is a chance that SysInfo is looking at the Host drive instead of the
boot drive. To correct this, add StartupDrive=<drive letter> in the [System
Information] section of the NDW.INI where "<drive letter>" is the correct
letter of the boot drive.